The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jameskoster <[email protected]>
Co-authored-by: ciampo <[email protected]>
Co-authored-by: tyxla <[email protected]>
Co-authored-by: jasmussen <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

I think there's a question about the visual style we want to apply across these docs, it may be good to decide on a specific illustration style (which could be what you suggested, but it could also be this), and then roll it out consistently.

I think as a first draft this is fine. What do you think? Nice work.

Rebased on top of latest changes, and pushed a couple of improvements / fixes.

In particular, I refactored the table so that it can be a more generic and work for both radius and elevation tokens. It's still a bit hacky, and we will definitely want to refine it (alongside other docs componentry)

@tyxla Since I was the last one to work on this PR (and I'm not sure about Jay's availability this week), I've addressed the remaining feedback.

Will merge as soon as CI checks pass ✅

Thanks @ciampo and @jameskoster 🙌